like switching to windows and launching applications. GNOME Shell takes
advantage of the capabilities of modern graphics hardware and introduces
innovative user interface concepts to provide a visually attractive and
-easy to use experience.
+easy-to-use experience.
All interactions with the project should follow the [Code of Conduct][conduct].
effective issue reports.
If you are using extensions, please confirm that an issue still happens
-without extensions. To properly disable extensions you can use the
+without extensions. To properly disable extensions, you can use the
[extensions-app] and then restart your session. Disabling extensions
without a restart is not sufficient to rule out extensions as the
cause of a bug. If an issue can only be reproduced with a certain
and reach out on the [#gnome-design matrix room][design-room],
and only involve the issue tracker once agreement has been reached.
-In particular mockups must be approved by the design team to be
+In particular, mockups must be approved by the design team to be
considered for implementation.
For enhancements that are limited in scope and well-defined,
It can be useful to first look at the [GNOME handbook][mr-handbook].
If a change likely requires discussion beyond code review, it is probably better to
-open an issue first, or follow the process for [feature requests](#feature-requests).
+open an issue first or follow the process for [feature requests](#feature-requests).
Otherwise, creating a separate issue is not required.
The following guidelines will help your change to be successfully merged:
## Documentation
- * [Coding style and conventions for javascript][js-style]
+ * [Coding style and conventions for JavaScript][js-style]
* [Coding style and conventions for C code][c-style]
* [The GJS Developer Guide][gjs-guide]
* [Building and Running][building]